Repository navigation
Conversation
Hard gates is done (Linear Done 2026-10-01; closure QA FIX-1636 passed on #2543). Its row moves to done, its graph node goes heavy, its arc bar closes Sep 29 to Oct 1, and the now line moves to Oct 1. Decided once gains three entries that bind sibling epics: the packed-install job permanently runs the two-users suite on installed tarballs (workspace-link control must fail, leg c refuses without Redis); BullMQ session concurrency is enforced by a Redis lease (FIX-1634); FIX-1665 and FIX-1658 are standalone follow-ups. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HNTQkGXCUryuVD2TEBLi6G
|
The latest updates on your projects. Learn more about Vercel for GitHub. 3 Skipped Deployments
|
Collaborator
Author
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Chef's kiss. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Public Launch takes FSD from "the framework runs" to "a stranger can install it, build with it, and not be hurt by it". This PR is the project's standing spec. It is never merged and stays open for the life of the project. It replaces #2359, which was merged by mistake on 2026-09-29 (cleanup on
main: #2392). It is a draft so it can't be merged again. As of 2026-10-01 · head960934c4.The fence asks whether a stranger would hit it, or be harmed by it, the day the doors open. Anything else ships on its own project's timeline, except framework simplification, which the launch waits for.
Hard gates closed in three days. The first hour is now the only open bar, and it is what the launch cut waits on.
The epics (live table): FIX-1161 first hour, in flight · FIX-1635 hard gates, done (closure QA passed on #2543) · docs, brand and demo bar, not filed · the launch cut, not filed.
Settled at the hard-gates wrap, binding every later epic (decided once): the packed-install job keeps running the two-users suite against installed tarballs, its workspace-link control must fail, and its queue leg refuses without Redis · BullMQ session concurrency is enforced by a Redis lease (FIX-1634) · FIX-1665 and FIX-1658 are standalone follow-ups, not hard gates.
Need your sign-off
Launch as 1.0, or as 0.x? A 1.0 launch promises installers we won't break them without a major version. It also turns every public API shape into a launch gate. Hard gates wrapped as a defect list, so 1.0 now means a separate API review before the cut. I recommend 0.x, stated plainly in the announcement, with 1.0 as its own milestone after the first cohort. I'd change my mind if a design partner or launch channel needs a stability promise on day one. Being wrong is one-way: 0.x to 1.0 later is cheap, breaking a 1.0 API costs trust. Full ask, with its trade-off figure: DECISIONS.md → Open. It comes down to the hard-gate bar: 1.0 turns a defect list into a full API review.
Reviewers · look here
absorbed/linear-content.md.Spec · Decisions · Rules · Plan · Linear project
How to review this
This is a project-spec: the standing outcome, the cross-epic decisions, and the live state of
one Linear project, in four documents. It is not an implementation plan, not any one epic's
objective, and not a design.
In scope to challenge:
That question can only be asked here.
DECISIONS.mdthat binds several epics, or a rule inBUSINESS-RULES.mdwith noowner or two.
Out of scope — owned by the epic specs below it:
the project moves and is never a review finding.
Feedback in the second list is routed to the epic it concerns, not folded in here.
🤖 Generated with Claude Code
https://claude.ai/code/session_01HNTQkGXCUryuVD2TEBLi6G
Generated by Claude Code